Release Upgrade Whonix 17 to Whonix 18
Jump to navigation
Jump to search

How to Release Upgrade from Whonix 17 to Whonix 18
Notices
[edit]Once available it will be announced in the usual places. See Stay Tuned.
| Notice | Description |
|---|---|
| Difficulty |
|
| Release Upgrade vs Re-Installation |
To use Whonix 18, users can either:
|
| Standard Updates |
|
| Automated Release Upgrade vs Manual Release Upgrade |
|
| Configuration Files Resets | Since this is an automated release upgrade, user modified configuration files (if any) in folder /etc will be reset, overwritten with the Debian or Whonix package version. The user is free to restore the configuration after the release upgrade.
|
High Level Overview
[edit]- Backup all data - ideally have a copy of the VM(s) so it is possible to try again (if necessary).
- Perform the usual standard ("everyday") update instructions.
- Release Upgrade Whonix-Workstation (
whonix-workstation-17). - Power off Whonix-Workstation (
whonix-workstation-17). - Release Upgrade Whonix-Gateway (
whonix-gateway-17). - Restart Whonix-Gateway (
whonix-gateway-17). - Restart Whonix-Workstation (
whonix-ws-workstation).
Platform Specific Notices
[edit]- Whonix: No special notice.
- Qubes-Whonix:
- Qubes R4.2: Unsupported for Qubes R4.2. [2]
- Qubes R4.3: Available for Qubes R4.3 and above only.
Release Upgrade
[edit]- Backup all data, ideally have a clone of the VM(s) so it is possible to try again (if necessary).
- Perform the usual standard ("everyday") update instructions.
- Consider running the optional sanity tests.
- Run systemcheck
. - View
release-upgradecommand version: cat /usr/sbin/release-upgrade | grep version= - Check
release-upgradecommand version. It should be a minimum of3.3, and displayversion="3.3". - Consider keeping the full release upgrade log output. It will be required for Support in case there are issues.
- Perform the automated release upgrade using the
release-upgradecommand: sudo release-upgrade - Re-run the repository-dist utility to update your derivative APT sources list from the old
.listto the new.sourcesformat. [3] This is a very minor issue if forgotten. It can be done at any later time. systemcheck will point this out if it has not been done yet. - Done. If everything went well, at the end it will show:
INFO: OK. (release-upgrade version: 3.3) Release upgrade success.
- Reboot.
- Optional, recommended: Re-install Meta Packages and Safely Run Autoremove
Support the Future of Whonix
[edit]Whonix is made possible thanks to the donation of people like you.
Please support the Whonix development with a donation.
Footnotes
[edit]- ↑
This method is still possible. All the automated
release-upgradescript does is perform actions which the user could perform manually. If a manual release upgrade is desired, emulate what the
release-upgradescript is doing. The manual release upgrading procedure is undocumented due to the size of the instructions and duplication involved. - ↑
- decide availability of Kicksecure, and Whonix 18 (Debian trixie based) on Qubes R4.2 versus R4.3

- Whonix 18 issue in Qubes R4.2 sdwdate-gui: qrexec
sdwdate.ConnectCheckdenied messages
(despite the name, sdwdate-gui issue, not sdwdate issue)
- Technically,
sudo release-upgrade --forcemight work for Qubes R4.2, but this is unsupported. - decide availability of Kicksecure, and Whonix 18 (Debian trixie based) on Qubes R4.2 versus R4.3
- ↑
https://forums.kicksecure.com/t/apt-sources-list-one-line-format-versus-deb822-style-format/267

We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 13 year success story and maybe DONATE!



